Libris Britannia 4/science library(b).zip/science library(b)/COMMUNIC/BULLETIN/0457.ZIP/RELEASE.NOT

Text File | 1987-03-01 | 8KB | 504 lines

                         ROS version 3.61 Release Notes


        This short document lists the changes and additions available in
        ROS 3.61 and only supplements the more complete documentation
        available with version 3.6.  Please refer to the ROSOPS.DOC for
        more information.

        ROS version 3.61 corrects all known Xmodem protocol transfer
        problems that were present in version 3.6, fixes some other minor
        bugs, and adds several new features.  Internal "flow" changes
        have been made to improve operation and appearance.

        No changes to the system data files are required, so you should
        be able to run 3.61 right away.  Just in case something catas-
        trophic happens, please back-up your current system before you
        start.

        Specific changes are described in subsequent paragraphs.

















































                          Interrupt Driven I/O Drivers

        Communications port I/O is now fully interrupt driven (thanks to
        Blaise Computing and their excellent tools) which improves the
        user response and makes the system much more amenable to multi-
        tasking.  Currently, the only multi-tasking environment that ROS
        is "aware" of is DESQview, but others should be added in the near
        future.

        The communications port driver uses a separate program, LCOMX.EXE
        which MUST BE RUN FIRST.  If not, ROS will issue an error message
        and quit.  This RAM resident program should be installed from the
        AUTOEXEC.BAT file.  It needs to be run only once, regardless of
        how many times ROS is brought up and down (without doing a warm
        or cold boot), and is also capable of supporting two copies of
        ROS simultaneously, e.g. under DESQview.  In other words, this
        program is RAM resident and should be run exactly one time each
        time the computer is brought up from a warm or cold boot.
















































                                   Status Line

        Several changes have been made to the status line.  Instead of
        cramming the access level, time on, and time left into one block,
        the time on and time left are separated with a diamond in one
        block.  The access level is by itself in the next block to the
        right.  The pulse indicator is now the time of day which alter-
        nates highlights to keep the screen from burning.


























































                             Command Line Parameters

        Three command line parameters are available in this version:

        /D   instructs ROS to ignore modem responses and clear-to-send
             (CTS) to assist in direct connections, i.e. directly
             connected to another computer instead of through a modem.

        /M   enables modem input and output display on line 24 of the
             display.  This is very useful when first setting ROS up with
             a new modem.  The left half of the line shows output to the
             modem, the right displays the modem responses (arrows in the
             middle of the line assist in remembering which is which).

        /O=x allows the sysop to specify a path to the ROS overlay files
             (ROS.00?).  If this parameter is omitted, ROS will try to
             find its overlay files in the default (current) directory.
             The value "x" may be set to any valid sub-directory on any
             disk drive, including a RAM disk.















































                                  New Commands

             Expert Mode Toggle:

        Users may now enter an "X" to toggle expert mode on and off, i.e.
        help level 1 or 3.  As sysop, you will still enter the sysop sub-
        system.  While there, an "X" will have the same response as for
        the users.

             Version Display:

        While in the sysop sub-system, enter a "V" for version.  ROS will
        display its internal version number, that of DOS, and of DESQview
        if present (other multi-tasking shells will soon be supported
        here as well).

             Time Initiated Macros:

        This first implementation of time initiated macros is very sim-
        plistic: at midnight (or after the caller logged in at midnight
        logs out), ROS will check the macro file for a line beginning
        with a colon (":").  If it finds such a line, it will start
        execution.  The macro, starting with the first character after
        the colon, will be played back to the system just as if the
        characters were coming from a remote site or from the local
        console.

        Since the system expects a valid login, you must include a user
        name and password in the macro.

        In this "Internal Login" mode, the pagination line counter is
        disabled so that ROS does not have to wait for a "More" response.

        A sample macro file, MACRO.ROS, demonstrates time initiated mac-
        ros.  This macro file logs in, purges all the system files,
        builds a system directory, and logs out.  You will have to add
        your own password in where it says "PASSWORD."

        The F7 function key may be used to simulate the passage of mid-
        night to facilitate testing of your macro.


























             DOS Shelling:

        DOS shelling is available in the sysop sub-system by pressing "J"
        for <J>ump to DOS.  If logged in remotely, ROS will require a
        batch file name.  If local, you may either enter a batch file
        (ROS will assume a file extent of ".BAT" if not specified) or
        simply press <RET>.  While in DOS, you may execute any normal DOS
        command (be careful with the ROS system files - they are still
        open!).  After all DOS commands have been completed, type "exit"
        to return to ROS where you left off.

        Using the DOS shell command remotely:

        DOS has an internal command "CTTY" which redirects standard
        console I/O to the specified device.  Normally, this device will
        be COMx where "x" is either 1 or 2, indicating the COM port that
        ROS was using.  For example, if your batch file contains the
        single line "CTTY COM1", when you jump to DOS remotely and tell
        DOS to execute this batch file, you will still have access to
        your computer even though you are now running DOS!  When you have
        completed your work in DOS, type "EXIT" to return to ROS where
        you left off.  CAUTION: to re-establish interrupt driven I/O with
        the Comm port, ROS has to close the port and then open it again.
        This will briefly drop DTR which may hang up the modem if it is
        set to respond to DTR.  If you need access to DOS remotely, you
        will need to set your modem so that it does not respond to the
        loss of DTR by hanging up.







































                                     Errors

        Apparently ROS does not get along very well with an EGA.  The
        incompatibility does not affect the remote user, nor does it
        cause any serious problems, but the local console can get messy.
        The problem will be corrected as soon as possible.

        To the best of my knowledge, 3.61 is very solid (except as noted
        above), but there is always a chance for undiscovered problems.
        If you have problems with the installation, or if your users have
        problems (especially with a particular modem package), please let
        me know.

                  Steve















































now.

                  Steve